If you are experiencing higher than normal CPU utilization with Lotus Notes Traveler, you should first open a PMR on the issue to determine if there is an underlying problem. To do so:

1. Start Tracing on the Lotus Notes Traveler server:
   
   

   Tell Traveler log level finest

   Tell Traveler log count 100 

   
   
2. Verify that the problem occurs.
   
3. Initiate a system dump:
   
   

   Tell Traveler SystemDump

   
   
4. Wait 5 or 10 minutes , then initiate a second system dump, as in step 3.
   
5. Wait for the system and NSD dumping to finish.
   
6. Collect the logs and send to IBM:
   
   

   Tell Traveler log collect

   Upload <DominoData>/IBM_TECHNICAL_SUPPORT/traveler/logs/<DatedFolder from step 6>

For a possible work around, you can also try to defragment the Lotus Notes Traveler database. It is best to do this during a scheduled outage, since the process could take 30 minutes or more to complete, depending on your system.

1. Shut down Lotus Notes Traveler:
   
   

   Tell Traveler Shutdown

   Tell HTTP Quit

   
   
2. Wait for Lotus Notes Traveler to shutdown completely, otherwise the defragmentation will fail. If Lotus Notes Traveler does not shutdown after a reasonable amount of time, issue the command "Tell Traveler Quit".
   
3. Once Lotus Notes Traveler is shut down, restart it using the "defrag" parameter:
   
   

   Load Traveler -defrag

   
   
4. After Traveler restarts, verify that HTTP has also started. If not, issue the command "Load HTTP".
   
5. Your system should be back up and running. Monitor the CPU to see if the defragmentation fixed the problem.